41 research outputs found

    Multi-person tracking using dynamic programming

    Get PDF
    Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2001.Includes bibliographical references (p. 75-77).This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.by Rania Y. Khalaf.M.Eng

    Coordination protocols for split BPEL loops and scopes

    Get PDF
    The document presents an approach to enable loops and fault handling, compensating scopes to be split among a set of BPEL processes running on different BPEL engines. A mechanism to split a scope or loop into multiple fragments is presented, then a protocol is defined that can be used to coordinate fragments of a loop or a scope so that those fragments run as if they had been in a single process. The requirements for running split scopes and loops are explained. For compensation, this paper focuses on explicit compensation and makes the assumption that compensation handing does not fail. Two protocols are defined such that they may be plugged into the WS-Coordination framework. The messages between the participant fragments and the coordinator are defined. The information about the participating processes that the coordinator needs to have is specified. An algorithm is provided to locate a fault handler in the hierarchy of scopes that can handle a particular BPEL fault. Additionally, the behavior of both participants and the coordinator are specified

    A Classification of BPEL Extensions

    Get PDF
    The Business Process Execution Language (BPEL) has emerged as de-facto standard for business processes implementation. This language is designed to be extensible for including additional valuable features in a standardized manner. There are a number of BPEL extensions available. They are, however, neither classified nor evaluated with respect to their compliance to the BPEL standard. This article fills this gap by providing a framework for classifying BPEL extensions, a classification of existing extensions, and a guideline for designing BPEL extensions

    An event model for WS-BPEL 2.0

    Get PDF
    This report presents an engine-independent WS-BPEL 2.0 event model. It supports both passive monitoring and active control of process execution by external applications. Some of the assumptions in the presented event model are inspired by a particular implementation, e.g. fault handling and compensation; however they are kept as general as possible, so that they can be mapped on other engine-specific approaches to tackle faults and support compensation. In addition, the report draws on the experience of some of the authors in business process management and software development. The overall BPEL event model consists of a set of event models for the different types of BPEL entities that change their states: processes, process instances, general activities, scope activities, invoke activities, loops, links, variables, partner links, and correlation sets. The event model is used by the authors of the report in several projects, all utilizing process life cycle events in different scenarios

    MLSys: The New Frontier of Machine Learning Systems

    Get PDF
    Machine learning (ML) techniques are enjoying rapidly increasing adoption. However, designing and implementing the systems that support ML models in real-world deployments remains a significant obstacle, in large part due to the radically different development and deployment profile of modern ML methods, and the range of practical concerns that come with broader adoption. We propose to foster a new systems machine learning research community at the intersection of the traditional systems and ML communities, focused on topics such as hardware systems for ML, software systems for ML, and ML optimized for metrics beyond predictive accuracy. To do this, we describe a new conference, MLSys, that explicitly targets research at the intersection of systems and machine learning with a program committee split evenly between experts in systems and ML, and an explicit focus on topics at the intersection of the two
    corecore